IRIX Base Documentation 1998 November/IRIX 6.5.2 Base Documentation November 1998.img/usr/share/catman/u_man/cat1/crontab.z/crontab

Text File | 1998-10-20 | 7KB | 133 lines

CCCCRRRROOOONNNNTTTTAAAABBBB((((1111))))                                                          CCCCRRRROOOONNNNTTTTAAAABBBB((((1111))))



NNNNAAAAMMMMEEEE
     crontab - user crontab file

SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
     ccccrrrroooonnnnttttaaaabbbb [file]
     ccccrrrroooonnnnttttaaaabbbb ----rrrr [file]
     ccccrrrroooonnnnttttaaaabbbb ----llll [file]
     ccccrrrroooonnnnttttaaaabbbb ----eeee [file]

DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
     _c_r_o_n_t_a_b copies the specified file, or standard input if no file is
     specified, into a directory that holds all users' crontabs.  The -r
     option removes a user's crontab from the crontab directory.  _c_r_o_n_t_a_b -l
     will list the crontab file for the invoking user. The -e option spawns an
     editor which contains the user's current crontab (as output by crontab
     -l), and automatically updates the crontab when the user saves the file
     and exits the editor. The name of the editor to invoke can be specified
     by the environment variable VISUAL or EDITOR; else, ed is used by
     default.

     Normal users may only remove, list, or edit their own crontab files which
     is the default.  The superuser (root) may supply any username following
     ----rrrr, ----llll, or ----eeee to remove, list, or edit that user's crontab.

     If the file ////eeeettttcccc////ccccrrrroooonnnn....dddd////ccccrrrroooonnnn....aaaalllllllloooowwww exists, only users whose names appear
     in the file are permitted to use _c_r_o_n_t_a_b. This restriction applies to all
     users, including root.  If that file does not exist, the file
     ////eeeettttcccc////ccccrrrroooonnnn....dddd////ccccrrrroooonnnn....ddddeeeennnnyyyy is checked to determine if the user should be
     denied access to _c_r_o_n_t_a_b. If neither file exists, only root is allowed to
     submit a job.  If ccccrrrroooonnnn....aaaalllllllloooowwww does not exist and ccccrrrroooonnnn....ddddeeeennnnyyyy exists but is
     empty, global usage is permitted.  The allow/deny files consist of one
     user name per line.

     A crontab file consists of lines of six fields each.  The fields are
     separated by spaces or tabs.  The first five are integer patterns that
     specify the following:

          minute (0-59),
          hour (0-23),
          day of the month (1-31),
          month of the year (1-12),
          day of the week (0-6 with 0=Sunday).

     Each of these patterns may be either an asterisk  (meaning all legal
     values) or a list of elements separated by commas.  An element is either
     a number or two numbers separated by a minus sign (meaning an inclusive
     range).  Note that the specification of days may be made by two fields
     (day of the month and day of the week).  If both are specified as a list
     of elements, both are adhered to.  For example, 0 0 1,15 * 1 would run a
     command on the first and fifteenth of each month, as well as on every
     Monday.  To specify days by only one field, the other field should be set
     to * (for example, 0 0 * * 1 would run a command only on Mondays).



                                                                        PPPPaaaaggggeeee 1111






CCCCRRRROOOONNNNTTTTAAAABBBB((((1111))))                                                          CCCCRRRROOOONNNNTTTTAAAABBBB((((1111))))



     The sixth field of a line in a crontab file is a string that is executed
     by the shell at the specified times.  A percent character in this field
     (unless escaped by \\\\) is translated to a new-line character.  Only the
     first line (up to a % or end of line) of the command field is executed by
     the shell.  The other lines are made available to the command as standard
     input.

     The shell is invoked from your $$$$HHHHOOOOMMMMEEEE directory with an aaaarrrrgggg0000 of sssshhhh....  Users
     who desire to have their ._p_r_o_f_i_l_e executed must explicitly do so in the
     crontab file.  _C_r_o_n supplies a default environment for every shell,
     defining HHHHOOOOMMMMEEEE,,,, LLLLOOOOGGGGNNNNAAAAMMMMEEEE,,,, UUUUSSSSEEEERRRR,,,, SSSSHHHHEEEELLLLLLLL((((====////bbbbiiiinnnn////sssshhhh)))),,,,
     PPPPAAAATTTTHHHH((((====////uuuussssrrrr////ssssbbbbiiiinnnn::::////uuuussssrrrr////bbbbssssdddd////::::////uuuussssrrrr////bbbbiiiinnnn::::////bbbbiiiinnnn////::::////eeeettttcccc::::////uuuussssrrrr////eeeettttcccc)))),,,, and TTTTZZZZ.

     If you do not redirect the standard output and standard error of your
     commands, any generated output or errors will be mailed to you.

     Any errors encountered while parsing the crontab file (or stdin) will
     cause _c_r_o_n_t_a_b to abort with no changes being made to any existing
     crontab.

FFFFIIIILLLLEEEESSSS
     /etc/cron.d                main cron directory
     /var/spool/cron/crontabs   spool area
     /var/cron/log              accounting information
     /etc/cron.d/cron.allow     optional list of allowed users
     /etc/cron.d/cron.deny      list of denied users
     /etc/cron.d/FIFO           to communicate crontab changes to _c_r_o_n

SSSSEEEEEEEE AAAALLLLSSSSOOOO
     sh(1), cron(1M)

NNNNOOOOTTTTEEEESSSS
     If you inadvertently enter the ccccrrrroooonnnnttttaaaabbbb command with no argument(s), you
     may exit without overwriting the existing crontab entry either by
     generating an interrupt (typically by typing ^C or DEL), or by providing
     empty input (typically by typing ^D on the first empty line).

     If a job is scheduled during the 'witching hour' - the time during a
     change from the main to alternate time zone, the job will either be run
     once (if the actual time exists twice) or not at all (if the actual time
     never exists).














                                                                        PPPPaaaaggggeeee 2222